HP X.400 UPDATE TRAINING May 29, 1991 The purpose of this message is to provide an overview of the changes in the C.02.00 release of HP X.400. In this release, the C.01.00 versions of X.400/9000 and X.400 Server Software have been merged into a single product called HP X.400. Note that the C.02.00 release, the X.400/HP Desk software (used with the former X.400 Server Software) product is not changing. This message is intended for SEs, CEs, RCEs, and HP division personnel who have been trained on or are familiar with HP's X.400 products and who need update training on the new release. It summarizes the major changes in the new release. This message is organized into the following sections: 1. Major New Features 2. Other Enhancements 3. Hardware/Software Requirements 4. Documentation Changes 5. New Utilities 6. Modified Utilities 7. Obsoleted Utilities 8. Side Effect Differences 9. Update Training 10. Updating Customers from C.01.00 to C.02.00 11. Distribution of Update to Field 1. Major New Features --------------------- The main enhancements in the C.02.00 release are described below. o X.400/9000 and X.400 Server Merged The X.400 Server and X.400/9000 products have been merged into one product. The combined product is called "HP X.400". The merged product allows HP Desk and Unix mail users to share a single X.400 gateway (previously HP Desk and Unix mail users had to have separate X.400 gateways). As a result of the product merge, the X.400 Server Software (32058A) has been discontinued and replaced by HP X.400. HP X.400 uses the former X.400/9000 product numbers (32031A/32032A). The Server bundle (32057A) remains but now includes HP X.400 instead of X.400 Server Software. The HP3000 portion of X.400 (the X.400/HP Desk software) is unchanged for this release. o High-Level X.400 API HP X.400 now provides a simple application programmatic interface (API) which allows programmers to write applications that can send and receive messages over a X.400 network. The nine intrinsics provide the basic X.400 functions (send and receive messages, send and receive delivery reports). Although the HP X.400 API is proprietary, it is less complex and easier to use than the XAPIA (X/Open API Association) gateway or application APIs. o 1988 MTA The MTA (Message Transfer Agent) in HP X.400 implements the functions defined in the CCITT 1988 X.400 standard. Some of these functions include: - Routing on 1988 O/R address fields such as those used for Physical Delivery Services (Physical Delivery Service is the ability to send a message over X.400 to a postal service which then prints the message and delivers it to the recipient). You can configure HP X.400 to route on the 1988 O/R address fields. However, the supported User Agents (HP Desk, Openmail, and mailx/elm) do not support these addressing fields at this time. - Support of T.61 characters in most of the address fields. The Teletex (T.61) character set includes accented characters used in other languages and can be used in the following fields: Organizational Name Organizational Units Domain Defined Attributes Personal Name Common Name (a new field for a name which does not fit into a X.400 personal name, e.g., a title such as "Director of Marketing") Note that T.61 fields can not be used with a 1984 X.400 system as it will not be able to understand or generate them. - Object Identifiers. In 1984 X.400, only text body part types are supported (anything else is considered an undefined body part). In 1988 X.400, other types of body parts can be used and each body part type is identified by a unique number called an Object Indentifier. With Object Identfiers, recipients know what type of body part the message is contains (e.g., Lotus 123 spreadsheet) and can handle it accordingly (e.g., run Lotus to view/modify body part). Note that the User Agents (HP Desk, OpenMail, mailx/elm) cannot generate or recognize Object Identifiers at this time. Support of Object Identifiers is a planned enhancement request for OpenMail (HP Desk does not plan to include 1988 User Agent (UA) functionality). o Billing Information Billing information can be logged to a file so that billing reports can be generated. The System Administrator can configure which information is to be logged such as originator, recipient, message type (message, probe, or report), message size, and priority. When X.400 is running, the configured billing information is logged to the billing file /usr/spool/x400/log/bill.log. When the configuration is enabled, a sample billing program customized to read the information in /usr/spool/x400/log/bill.log is created in the file /usr/lib/x400/ex_applic.c. The System Administrator can develop a program to read the billing file and calculate the appropriate charges to the users based on this sample program. o User Groups User groups are a way to categorize users if not all the users have the same capabilities. For example, users on 1984 X.400 systems can be in one group and users on 1988 X.400 systems can be in another. When 1988 X.400 users exchange messages, they can take advantage of the additional functionality provided in 1988 X.400. User groups can also be used to control which users can send or receive messages. A User Group can be designated as "send only", "receive only", "send and receive", or "neither send nor receive". User groups are identified by a combination of the following X.400 address fields: Country, ADMD, PRMD, Organizational Name, or Organizational Units. In addition to access control (restricting send/receive capabilities), each User Group can also be configured for the character set understood by the group(T.61, ISO6937, or IA5), profile the group conforms to (EWOS88, NIST84, NIST88, CEN41201, or CEN41202), and whether address translation is required for users in this group (see address translation below). o Address Translation Each MTA in a PRMD is supposed to be connected to only one ADMD. By changing an MTA's Global Domain Identifier (combination of Country, ADMD, and PRMD), a single MTA can be connected to multiple ADMDs. This is referred to as address translation. Address translation changes the Global Domain Identifier of a message and all addresses of users belonging to user groups for which address translation has been requested (see User Groups above). Two cases where address translation might be useful are: - When a single MTA wants to connect directly to more than one MTA. This is possible in countries where more than one ADMD exists. For example, suppose an MTA located in the U.S. and belonging to PRMD "X" wants to connect to ATTMAIL and TELEMAIL (both are U.S. ADMDs). The MTA's Global Domain Identifier would need to be Country=US, ADMD=ATTMAIL, PRMD=X when talking to ATTMAIL, and Country=US, ADMD=TELEMAIL, PRMD=X when talking to TELEMAIL. - When the originator is from another country but wants to appear (to the ADMD) to be from the local country. For example, an originator in the U.S. wants to send a message to France but wants his O/R address to be Country=FR, ADMD=ATLAS, etc. Worldwide companies may want this feature to reduce ADMD costs (it may be less expensive to route a message from U.S. to France within the PRMD than use an ADMD to ADMD (ATTMAIL to ATLAS) connection. Another reason worldwide companies may want to change the originator's O/R address is that some ADMDs do not accept messages from a PRMD which is not in the ADMD's domain. For example, employees in Country=A, ADMD=X, PRMD=Z cannot send messages to ADMD "Y" because ADMD "Y" only accepts messages from Country=B, ADMD=Y, PRMD=Z. Employees in Country "A" need to have their Country and ADMD address fields "translated" before they can send messages to Country "B." Note that address translation may be forbidden by national regulations in some countries. 2. Other Enhancements --------------------- Other enhancement to HP X.400 are: o Maximum number of simultaneous connections increased to 32. o Long file names are no longer required. o The *.conf.new files are created only when the user makes a configuration change (hits Perform Task). In the C.01.00 release, the *.conf.new files were created when the user entered the configuration menu. 3. Hardware/Software Requirements --------------------------------- Hardware Requirements: o HP 9000 Series 300, 400, or 800 o 802.3 LAN Card (if LAN connectivity desired) o X.25 Card (if X.25 connectivity desired) o 1/4" cartridge or 9-track reel tape drive o 8MB (or more) or memory o 12MB of disk space: 8MB for HP X.400 and 4MB for message store o 30MB (or more) or swap space Software Requirements: The C.02.00 X.400 release requires HP-UX 8.0 and C.02.00 OTS. Below is a matrix comparing the software requirements for C.01.00 and C.02.00 releases. X.400/9000 X.400 Server | HP X.400 (C.01.00) (C.01.00) | (C.02.00) ---------- ---------- | ------------ HP-UX: 7.0 7.0 | 8.0 | ARPA: 7.0 N/A | 8.0 | X.25: A.07.00 A.07.00 | A.08.00 | OTS: C.01.00 C.01.00 | C.02.00 | OpenMail(1): A.00.00(2) N/A | A.00.01 OR | A.00.01 | | NS/9000 N/A 7.0 | 8.0 N/A = Not Applicable (1) OpenMail is not required for X.400/9000. However, if you want to run X.400/9000 with OpenMail, you must have the specified version. Also, OpenMail A.00.00 does not provide X.400 access on the Series 300. Note that OpenMail before A.00.01 was not supported on the Series 300. (2) To run X.400/9000 with the A.00.00 version of OpenMail, you must install a patch to modify some OpenMail files to be compatible with the X.400/9000 file permissions. The patch (patch number OM000004) can be obtained from PWD's patch machine or the hpfcse patch machine in Ft. Collins, Colorado. The next release of OpenMail (A.00.01) will not require the patch. The X.400/HP Desk software requirements are the same as before as X.400/HP Desk did not change for this release. Systems running the C.02.00 HP X.400 software can communicate with systems running the C.01.00 X.400/9000 or X.400 Server software and vice versa. 4. Documentation Changes ------------------------ With the product merge, the HP X.400 Server Administrator's Guide (32058- 90001) is being obsoleted and replaced by the Installing and Administering HP X.400 Administrator's Guide (32034-90001). 5. New Utilities ---------------- The following diagnostic utilities are new for this release: x4solve - displays error messages on-line. The user enters in an error number and x4solve displays the error message, cause, and action text. Since x4solve allows the user to view error messages on-line, the error messages in the manual have been removed. The user can print the error messages to a printer if a paper copy is desired. 6. Modified Utilities --------------------- The following commands have been modified for this release: x4agelog - keeps the latest 200 entries in the /usr/spool/x400/log/dslog directory (previously x4agelog did not delete any entries in the dslog directory). x4dump - now appends ASCII versions of the X.400 and OTS error log files to the shar output file (x4dump.sh). This is accomplished by running x4logview (for X.400 errors) and otsfmt (for OTS errors) to convert the error log files from binary to ASCII format before appending them to x4dump.sh (previously the unformatted binary error log files were appended). x4msgtrack - now tracks messages from an X.400 API client and all messages handled by the MTA (in addition to messages from Sendmail and HP Desk that x4msgtrack handled before). Selecting messages is done by entering a simple index (1, 2, 3 ...) instead of a long filename. x4queview - messages to be viewed are now selected by entering a simple index (1, 2, 3 ...) instead of a long filename. Also, the path of the directory no longer needs to be explicity entered. When x4queview encounters a bad PDU (parsing error), it will automatically run x4asnview to view the bad PDU. Before, x4queview just aborted if a bad PDU was detected. x4stat - reports status of logging for billing (on/off). 7. Obsoleted Utilities ---------------------- The following commands have been obsoleted for this release: << ANY OBSOLETED UTILITIES? >> 8. Side Effect Differences -------------------------- The following changes resulted from implementing the new features but do not have any impact on the use or operation of X.400: o As a result of long filenames no longer being required, the default.conf file has been renamed to deflt.conf. 9. Update Training ------------------ This message is the update training for SEs/CEs/RCEs trained on X.400. No further training will be provided. 10. Updating Customers from C.01.00 to C.02.00 ----------------------------------------------- Customers on the appropriate software support services will receive the new release (C.02.00) at no cost. The customer is responsible for doing the update. To update customers to C.02.00 X.400, install the dependent software (see Section 3) and load X.400 onto the system. Do not overwrite the existing X.400 configuration files. No further action is required. 11. Distribution of Update to Field ----------------------------------- The C.02.00 release of HP X.400 will be shipped with the HP 8.0 Application Release (AR) to all field offices on the following internal subscription services: 5062-7195 Field Demo and Education Center 5062-7196 RC/CEC/On-Line Support 5062-7197 Area/Branch Offices 5062-7179 System Documentation Library As of this writing, internal shipments should be completed by June 11 for Series 800 and July 2 for Series 300.